An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I am using CI/CD method to build my apps, i dont have xcode simulator, so I cannot produce 13'' screenshots And I have an ipad that is NOT 13'' what can I do? I am locked out from releasing on ipads?

Hello, I don't understand why Apple states that app reviews typically take 48 hours. In my experience, it has never been completed within 48 hours. It is usually at least 6–7 days, and in some cases I have waited up to two weeks just to receive a response. Another issue is that they never seem to provide all the problems clearly at once. I wait for a response, they point out one issue, I fix it, then after another week or two they identify a different issue that was already present from the beginning. This makes the entire process extremely slow and frustrating. Is there any way to get a faster response from the review team? Has anyone else experienced similar issues with App Review? Thank you.

Expedited review requested 24h ago but no response, missed launch date

Hi there, this is my first app, so please be gentle. I submitted it on 6/16 (3 days ago) and I saw somewhere that it took 24-48 hours to be reviewed, and I believe that's when the people I invited to test it would start getting their email invitations. It's still at "Waiting for Review" on the Test Flight tab. Is this the same as THE "app review"? Or is it some "mini-review" for Test Flight? Either way, when should I start following up?

Hello, I am reaching out regarding a critical review delay affecting Summer Rockz (App ID: 6763247379), a European festival discovery app. Version 2.0.0 has been in "Waiting for Review" since June 16, 2026 at 17:30 CET with no movement. Review history for v2.0.0: June 3 — Submitted for review June 4 — Rejected (Guideline 1.1) June 4 — Addressed and resubmitted same day June 16 — Rejected again (Guideline 1.1) June 16, 17:30 — All issues addressed and resubmitted Today, June 19 — Still "Waiting for Review", 3 days with no status change What I have already done: Submitted an Expedited Review request with a documented business justification (summer festival season, time-critical launch window) Opened multiple support tickets Responded in detail to both rejection notices via the Resolution Center Why this is urgent: Summer Rockz serves a seasonal audience tied to the European festival calendar. June and July are the peak months. Every day of delay directly impacts active users and partner festivals that depend on the app being live. The app has no unresolved guideline issues. Both rejection points were addressed immediately and documented in the Resolution Center. Could someone from the App Review team investigate whether this submission is stuck or flagged? I am not asking to bypass the process — I am asking for visibility on a submission that appears frozen with no review activity after 3 days. Thank you.

Hi everyone, I'm hoping someone from App Review (or anyone who's been through this) can help, because I'm a bit stuck. My app Mingle (Apple ID: 6770285096, Version 1.0.1) has been sitting in "Waiting for Review" for well over a week now. I first submitted at the start of June, and after it sat there for ~6 days with no movement at all, I figured something might be wrong, so I canceled and resubmitted. The new one has now been waiting since June 15 with the same silence: Submission ID: c919ad21-902a-4a3c-a6cc-a5fbd9f7e2b1 Every previous review of this app went through in under 48 hours, so this is really out of the ordinary. I've already opened a support request through Contact Us, but I haven't heard anything back yet. This is genuinely blocking me - I've been trying to get this release out since the beginning of the month and everything on my end is ready and waiting on the review. Is there anything I can do to move this along, or any reason a submission would get stuck like this? If anyone from App Review could take a look, or point me to the right channel, I'd really appreciate it.

Hello everyone, my application has been stuck in the "Information Submitted" status of Apple's review process for several weeks now. The system shows "Thanks for providing additional information—it is currently processing and will be reviewed shortly," but there has been no progress. During this time, I cannot access App Store Connect, and payments may be delayed. This situation has continued for weeks, seriously affecting my development and operational plans. Has anyone experienced a similar situation? Are there any methods to contact Apple to expedite the process or understand the specific reason for the delay? What additional information should I provide to move the review process forward? Thank you for your suggestions and help! @Apple

Hi, My app The Gold Standard (shown as "TGS" on the home screen, Apple ID: 6755989671) is a first-time submission. It was submitted on 26 May 2026 and has been in "Waiting for Review" status ever since — now around 4 weeks with no movement. I have followed up with Developer Support twice by email since submitting, but have only received automated "we've received your request" replies, with no follow-up and no change in status. There are no messages, rejections, or unresolved issues showing in App Store Connect, and no action appears to be required from my side. Could the App Review team please take a look and let me know whether the submission is simply in the queue, or whether anything is needed from me to help it proceed? I'd be grateful for any update. Thank you.

Hello, My app has been stuck in "Waiting for Review" status for 8 days now (since June 11), well beyond the standard 24-48h window. This is a resubmission after addressing all issues from a previous rejection. I have already: Submitted an expedited review request (no response) Sent an email to App Review 3 days ago (no response) Submission ID: cd753837-a630-460f-9459-46881ef599cd Has anyone experienced similar delays recently? Any advice on how to get an update would be appreciated. Thank you.

Hi all, I'm launching my first iOS app (Capacitor/Next.js WebView wrapper) with two auto-renewable subscriptions via RevenueCat, and I'm stuck on a persistent issue across multiple App Store Review rejections. Setup: Bundle ID: no.skaren.app Two auto-renewable subscriptions: no.skaren.app.premium.monthly and no.skaren.app.premium.yearly, both in a single subscription group RevenueCat integrated via @revenuecat/purchases-capacitor App-Specific Shared Secret added to RevenueCat App Store Connect API key (with correct Key ID/Issuer ID) added to RevenueCat Paid Apps Agreement: Active Bundle ID in RevenueCat matches exactly RevenueCat API key in app code matches dashboard exactly The problem: On a physical device (TestFlight build, signed into Sandbox Apple ID), calling Purchases.getOfferings() always returns: {"current":null,"allKeys":[]} No errors are thrown — the offerings object is just empty. This happens consistently across multiple builds, after removing a conflicting limitsNavigationsToAppBoundDomains WebView restriction (which was separately causing a blank-screen bug, now fixed and confirmed working on-device). App Store Connect status: This is our first subscription submission ever. Both subscription products currently show "Developer Action Needed" status in App Store Connect (their localizations were rejected once for vague wording, fixed and resaved, but the products remain in this state). App Review's rejection message explicitly states: "Apple reviews In-App Purchase products in the sandbox and the In-App Purchase products do not need prior approval to function in review." However, our experience suggests otherwise — RevenueCat returns zero offerings, and App Review's own testers also report an "error message displayed on the subscription page" when attempting to test the IAP flow. Question: Is it actually true that subscriptions in "Developer Action Needed" / not-yet-approved status can still be fetched via StoreKit/RevenueCat during sandbox testing? Or does the first-ever subscription submission genuinely need to be approved (i.e., go through the review cycle once) before getOfferings() will return populated data? Has anyone encountered this exact "chicken-and-egg" situation, where the first IAP submission can't be tested until reviewed, but review fails because it can't be tested? Any insight into whether this is expected sandbox behavior for first-time subscription submissions, or whether there's a configuration issue I'm missing, would be hugely appreciated. Thanks!

The app is waiting for review since April 22 (nearly 2 months!) with no sensible outcome. The first review never happened I contacted support several times and after more than 40 days I just deleted the submission and created a new one which was quickly rejected on June 3 with the following reasons: The app contains hidden features. The app provides a limited user experience as it is not sufficiently different from a web browsing experience. The reasons do not reflect the reality and I explained why this fully native app, high performance app can't be considered as it provides a limited user experience nor does it contain any hidden features. I referred to the video and explained the tech stack that could falsely trigger any webview concerns. On June 9 I had a call with Apple representative. Before anything the representative suggested for me to do something else in life and not chase the outcome of the review (!). In the end of the meeting he suggested I submit the appeal and so I did right after the call. 30 minutes later I was contacted via mobile by the same representative and he asked to not submit the appeal as they might have a resolution for my review and should just resubmit the same version. I did as suggested and the app has been waiting for review ever since with no communication whatsoever. Does anyone else have similar experience? Anything I can do at all? Submission ID c37cc165-1f58-435a-a394-35fbbee787f8

Hello Apple Staff, I’m posting again because this issue has not been resolved yet. We currently have two active apps under the same developer account that are still in Waiting for Review. For one of the affected apps, the details are as follows: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 We also tried to submit an expedited review request, but the expedited review form does not complete successfully. The following error message is displayed: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” Could Apple Staff please check the current status of these review submissions and let us know if any additional action is required from our side? We would greatly appreciate your assistance, as the review process has not started and we are currently unable to submit an expedited review request. Thank you for your time and support.

Hello App Review Team, My app, SUB PREMIUM TV (Apple ID: 6769972609, Version 1.0), has been in “Waiting for Review” status for several days. I would like to confirm whether there is any issue with my submission or if any additional information is needed from me. Thank you for your time and assistance. Best regards, Babucarr Ngum

Hello App Review team - My app(App ID: 6756242440) is stuck in 'Waiting for review'. Once in a while updates are getting stuck like this, while other times same app reviews go through in 48 hours. Please help us understand any reasoning behind this so we can plan our development accordingly. Thanks in advance!

This is our second App Store submission for Rex, a social entertainment discovery app whose core features depend on account-based personalization, saved history, and social/group functionality. Rex’s core features include Rex AI, which provides personalized movie and TV recommendations, along with social watchlists and Party Mode for group recommendations. These features do not function in any meaningful way without an account because they rely on user preferences, saved history, social connections, and persistent recommendation data to deliver the intended experience. Our app is being rejected under Guideline 5.1.1(v), even though account-based functionality is central to the premise of the product. Sign-in is not being used as a gate in front of otherwise accessible content. It is required because the product itself depends on an account-based experience. We have now received the same generic rejection message twice, with no indication that our previous responses were reviewed or considered. We submitted detailed explanations of how Rex works and why sign-in is foundational to the experience, but those points have not been acknowledged or addressed. The responses we have received do not engage with the specific nature of our app, do not address the 5.1.1(v) exception for apps whose core functionality is account-dependent, and appear to repeat the same form language without responding to the context we provided. This is a significant investment of time and resources, and we are trying to understand what Apple is specifically asking us to change. We are not trying to gate free content behind a login. We are trying to ship a product that, by design, requires an account for its core functionality to work. Can someone from Apple or the developer community help clarify how Guideline 5.1.1(v) should be applied to apps where personalization, social features, saved history, and group recommendations are the core product experience?

Hi everyone, App Name: StAIle Build: 6 (Version 1.0.0) I submitted this build for TestFlight external testing on June 12, 2026. It has been stuck in "Waiting for Review" status ever since (6+ days now), well beyond the typical 24-48 hour window. What I've tried so far: Sent an email to App Store Connect support — no response after 2+ days Submitted an expedited review request via the official form — still waiting on that too No message in the Resolution Center, no compliance flag I'm a solo developer trying to run external beta tests before submitting the app for full App Store review, and this delay is blocking that step entirely. Has anyone else experienced something similar recently, or found a way to get this moving? Any advice appreciated. Thanks!

I’ve been using the Age Assurance support page and related Developer News posts as the source of truth for understanding Apple’s expectations around Age Assurance on Apple platforms: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/news/?id=sg176nne Can anyone from Apple clarify whether anything has recently changed with App Review expectations related to Age Assurance? Specifically, are there any new requirements or updated guidance around implementing technologies like DeclaredAgeRange or PermissionKit? I didn’t see any sessions or announcements that indicated these frameworks are now required but with all of the new child safety announcements I thought I'd ask and document for the developer community. I did see the new sample code for implementing Age Assurance and permissions, but nothing suggesting their use is mandatory for App Store approval. https://developer.apple.com/documentation/declaredagerange/implementing-age-assurance-and-permissions Just trying to confirm whether current guidance remains the same, or if App Review expectations are evolving.

I have been waiting for 18 days for review my app. I don't know why or because many app AI Slop is waiting for review?

Body We are currently evaluating an architecture approach for an iOS application and are looking for guidance on App Store Review expectations and platform limitations. Context We are modernizing an existing healthcare application that handles regulated data (PHI). The application is intended for use by internal staff and authorized third-party contractors (not a consumer-facing app, and no monetization). To support iOS distribution, we are evaluating packaging an Angular-based Progressive Web App (PWA) using a lightweight native wrapper (e.g., via PWABuilder), resulting in a WebView-hosted application. Proposed Architecture Angular PWA hosted remotely and loaded via HTTPS Packaged inside a native iOS container (WKWebView-based) Authentication via Passkeys (WebAuthn / FIDO2) Backend APIs implemented in .NET Limited offline functionality using IndexedDB (non-sensitive data only) No persistent storage of sensitive data on-device The native wrapper primarily provides distribution and lifecycle management; most functionality is delivered via the hosted PWA. Key Consideration This application is not intended to function as a general-purpose browser, but rather as a purpose-built, workflow-specific experience for healthcare operations. Questions 1. App Review / Guideline 4.2 Have developers had success getting WebView-hosted applications (primarily PWA-driven) approved when they provide a complete and production-grade user experience? How does Apple typically evaluate whether such an app meets the “minimum functionality” requirement versus being considered a repackaged website? 2. Dynamic Content / Updates Are there specific restrictions on delivering functionality dynamically via server-hosted content after app approval? At what point would backend-driven changes require a new App Store submission? 3. Data Storage & WebView Behavior Are there notable differences in how iOS handles storage (e.g., IndexedDB, local storage) in: Safari-installed PWAs WebView-based apps distributed via the App Store? Are there known limitations or caveats when relying on IndexedDB within WKWebView? 4. Platform Capabilities Are there practical limitations for WebView-based apps related to: Offline functionality File handling Long-term platform support 5. Healthcare / Regulated Data For apps handling regulated healthcare data (PHI), are there additional expectations or best practices (beyond standard guidelines) that Apple reviewers typically look for? Goal We are trying to determine whether this architecture is viable for App Store distribution before proceeding further with implementation. Any insights, experiences, or pointers to relevant documentation would be greatly appreciated.

I submitted my app to App Review on June 5, 2026, and it has remained in the "Waiting for Review" status ever since. As of today, it has been waiting for review for 16 days without any updates from Apple. This is my first time experiencing such a long delay, and I wanted to ask if anyone else is facing similar review times recently or if there is anything I can do to expedite the process. App Details: Submission Date: June 5, 2026 Current Status: Waiting for Review Waiting Time: 16 Days Any guidance or shared experiences would be greatly appreciated. Thank you.